| It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Associating event types with detected events in the logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured firewall. Without this capability, it would be difficult to establish, correlate, and investigate the events related to an outage or attack.
Please note the distinction between logging and auditing; they are not the same, but they are closely related; auditing is a part of logging. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.
Log records must identify enclave and sub-enclave, node names, network element name, module, and sub-system as accurately as possible. Log messages sent to log servers must use a loopback address or management interface address as the source address. Using a loopback or management interface address as the source address simplifies management and security since it is easier to construct appropriate filters. A loopback address is less likely to become unavailable since it is usually not dependent on a single physical interface. Log information recorded by authentication and log servers will record the firewall implementation loopback or management interface address. |
